chore: remove deprecated Groq models and add new llama3.3 #3706
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for continuedev canceled.
|
3 tasks
|
any other thing I should do to get this PR merged? |
|
When I can use this fix? |
RomneyDa
previously approved these changes
Jan 27, 2025
RomneyDa
approved these changes
Jan 27, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Deprecated groq models (no longer available on their suported models list here):
and for new llama3.3 is being setup to be the replacement of previous llama3.1 as stated here https://console.groq.com/docs/deprecations
it is not urgent since people can manually configure its own model name, but it'll be nice to keep that auto complete in sync with current groq models
Checklist
Screenshots
[ For visual changes, include screenshots. ]
Testing instructions
[ For new or modified features, provide step-by-step testing instructions to validate the intended behavior of the change, including any relevant tests to run. ]